You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The post embeds in Discord, clicking the link opens the post
Actual behaviour
Post does not embed, clicking the link shows a completely useless warning
Detailed description
Clicking the above link will show the following page:
I don't see the point of this warning at all – it's only shown if you're not logged in in the directly linked instance, and I've only ever seen the warning shown when redirecting to other Fediverse instances. The warning probably also breaks embeds on other services, which used to work in the past.
These "roadblocks" are an important aspect of trust & safety, and were recently added to ensure users weren't phished or otherwise manipulated by an open redirect, which was previously the case.
An improvement we could add is a HTTP Link rel=canonical to these redirects that automated software can parse in a standardised way to discover the canonical link instead of the redirect & then embed that link instead of the instance's cached URI for that post
Steps to reproduce the problem
Expected behaviour
The post embeds in Discord, clicking the link opens the post
Actual behaviour
Post does not embed, clicking the link shows a completely useless warning
Detailed description
Clicking the above link will show the following page:
I don't see the point of this warning at all – it's only shown if you're not logged in in the directly linked instance, and I've only ever seen the warning shown when redirecting to other Fediverse instances. The warning probably also breaks embeds on other services, which used to work in the past.
Mastodon instance
mastodon.social, infosec.exchange, others.
Mastodon version
v4.3.0-nightly.2024-05-13, v4.3.0-alpha.3+glitch
Browser name and version
Multiple browsers (Vivaldi 6.7.3329.19, Firefox 126.0)
Operating system
Windows 11 22631.3593
Technical details
No response
The text was updated successfully, but these errors were encountered: